Sourced from @​tinacms/cli's releases.

@​tinacms/cli@​2.4.2

Patch Changes

• #6946 e729ed9 Thanks @​Aibono1225! - Add regression coverage for loading self-hosted database adapters through ConfigManager.loadDatabaseFile(), including memory-level, sqlite-level, mongodb-level, and the local Tina database client path.

• Updated dependencies [5c216dd, c7b366c, f7a2e5a]:

  • @​tinacms/graphql@​2.4.3
  • tinacms@3.8.4
  • @​tinacms/schema-tools@​2.8.1
  • @​tinacms/search@​1.2.17
  • @​tinacms/app@​2.5.2

@​tinacms/cli@​2.4.1

Patch Changes

• Updated dependencies [7be8175]:
  • @​tinacms/app@​2.5.1
  • tinacms@3.8.3

@​tinacms/cli@​2.4.0

Minor Changes

• #6790 542c781 Thanks @​Ben0189! - Fix native SQLite (and other native CJS adapters) crashing the ESM database build, plus surrounding cleanup work.

  The bug. Since Tina v3's December 2025 ESM migration, bundling tina/database.ts with esbuild — and writing the output to os.tmpdir() — left users wedged between two failure modes: bundling native modules like better-sqlite3 crashed with __filename is not defined, and externalizing them couldn't resolve node_modules from /tmp/. See #6675.

  What changed:

  • loadDatabaseFile and loadConfigFile now write esbuild output to <project>/tina/__generated__/.cache/<timestamp>/ instead of os.tmpdir(), so Node's resolver can walk up to the project's node_modules at runtime.

  • better-sqlite3 is externalized so Node loads it as CJS where __filename exists.

  • The build cache is swept on startup (clears residue from crashed prior runs), and each per-build subdir + its now-empty timestamp parent are removed after the dynamic-import resolves.

  • Read-only project mounts (Docker :ro volumes, AWS Lambda's /var/task, sandboxed CI runners) now fail with an actionable error explaining the cause and resolution, instead of a cryptic mid-build EACCES.

  • New defineConfig field: build.externalDependencies?: string[]. Users with custom native adapters outside the baseline can extend the externalize list from their config:

    // tina/config.ts
    export default defineConfig({
      build: {
        publicFolder: "public",
        outputFolder: "admin",
        externalDependencies: ["my-custom-native-adapter"],
      },
      // ...
    });

... (truncated)

Sourced from @​tinacms/cli's changelog.

2.4.2

Patch Changes

• #6946 e729ed9 Thanks @​Aibono1225! - Add regression coverage for loading self-hosted database adapters through ConfigManager.loadDatabaseFile(), including memory-level, sqlite-level, mongodb-level, and the local Tina database client path.

• Updated dependencies [5c216dd, c7b366c, f7a2e5a]:

  • @​tinacms/graphql@​2.4.3
  • tinacms@3.8.4
  • @​tinacms/schema-tools@​2.8.1
  • @​tinacms/search@​1.2.17
  • @​tinacms/app@​2.5.2

2.4.1

Patch Changes

• Updated dependencies [7be8175]:
  • @​tinacms/app@​2.5.1
  • tinacms@3.8.3

2.4.0

Minor Changes

• #6790 542c781 Thanks @​Ben0189! - Fix native SQLite (and other native CJS adapters) crashing the ESM database build, plus surrounding cleanup work.

  The bug. Since Tina v3's December 2025 ESM migration, bundling tina/database.ts with esbuild — and writing the output to os.tmpdir() — left users wedged between two failure modes: bundling native modules like better-sqlite3 crashed with __filename is not defined, and externalizing them couldn't resolve node_modules from /tmp/. See #6675.

  What changed:

  • loadDatabaseFile and loadConfigFile now write esbuild output to <project>/tina/__generated__/.cache/<timestamp>/ instead of os.tmpdir(), so Node's resolver can walk up to the project's node_modules at runtime.

  • better-sqlite3 is externalized so Node loads it as CJS where __filename exists.

  • The build cache is swept on startup (clears residue from crashed prior runs), and each per-build subdir + its now-empty timestamp parent are removed after the dynamic-import resolves.

  • Read-only project mounts (Docker :ro volumes, AWS Lambda's /var/task, sandboxed CI runners) now fail with an actionable error explaining the cause and resolution, instead of a cryptic mid-build EACCES.

  • New defineConfig field: build.externalDependencies?: string[]. Users with custom native adapters outside the baseline can extend the externalize list from their config:

    // tina/config.ts
    export default defineConfig({
      build: {
        publicFolder: "public",
        outputFolder: "admin",
        externalDependencies: ["my-custom-native-adapter"],
      },
      // ...
    });

    Externalized packages must be installed in the project's node_modules so Node can resolve them at runtime.

... (truncated)

• 07a6718 Version Packages (#6999)
• e729ed9 Add adapter compatibility test (#6946)
• ed213d6 Version Packages (#6983)
• c3eb837 Version Packages (#6858)
• 8ac0776 Fix typos: notifiySubscribers → notifySubscribers, Error occured → occurred (...
• 638b47a test(@​tinacms/cli): lock down loadDatabaseFile esbuild contract (#6864)
• c8b4ecb 📊 Add PostHog telemetry to tinacms build (#6841)
• 542c781 Fix native SQLite crash in ESM database build (#6790)
• a405781 Version Packages (#6852)
• 629af08 Fixing up imports (#6850)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)